You are here: Programming guide > COM SDK fundamentals > Creating a user interface extension > Debugging an interface extension

Debugging an interface extension

Debug your interface extension code by running the Visual Basic project in debug mode just as you would any other Visual Basic project.

Following are the basic steps involved in debugging an interface extension:

  1. Make sure the extension is registered in the vault. This can be done with the Testing tab of the interface extension designer.
  2. After setting breakpoints in the code that requires testing, run the project (press F5).
  3. If the debugging option of the project is set to Wait for components to be created, you must manually start the Meridian Enterprise PowerUser to test the extension.

Tip    Use the Start program option and enter the path to the PowerUser executable to automatically start the program whenever you run the project in debug mode.

  1. Visual Basic will stop code execution at the breakpoints so that you can resolve bugs as you test the functionality from the Meridian Enterprise PowerUser.

Note    If the breakpoints do not seem to work, check that the Version Compatibility setting on the Component tab of your project’s properties is set to Project Compatibility and select the extension’s .DLL file.

Make sure the project is compiled using the Project Compatibility or Binary Compatibility options as shown in the following figure. If not, then the Meridian Enterprise client applications will not use the instance of the interface extension that is being debugged.

Related information

About the Testing tab


www.bluecieloecm.com